Tree

There is a problem

1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

0625

reference: 901-tree-1
name: 0625
tree-preservation-order: undefined
901-tpo-1
uprn
address-text
point: POINT (-0.964195 50.861221)
geometry: MULTIPOLYGON (((-0.964095 50.861210,-0.964100 50.861230,-0.964114 50.861247,-0.964135 50.861261,-0.964163 50.861271,-0.964193 50.861274,-0.964224 50.861271,-0.964252 50.861262,-0.964275 50.861249,-0.964289 50.861231,-0.964294 50.861212,-0.964290 50.861192,-0.964276 50.861175,-0.964254 50.861161,-0.964227 50.861151,-0.964196 50.861148,-0.964165 50.861151,-0.964138 50.861159,-0.964115 50.861173,-0.964101 50.861191,-0.964095 50.861210)))
notes
felled-date
entry-date: 2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL